Job processing apparatus, method for controlling job processing apparatus, and storage medium for displaying a record of an executed job

ABSTRACT

A user is enabled to check a history of job execution by viewing records arranged in chronological order and to easily check the specific description of an error by viewing an error record. The job processing apparatus control method includes executing a job, displaying a plurality of history records with the plurality of history records being arranged side by side in chronological order, the plurality of history records each indicating a history of a job executed in the executing, and detecting an error. In response to an error having been detected in the detecting, an error record is displayed with the error record and the plurality of history records being arranged side by side, the error record indicating the error.

BACKGROUND Field of the Disclosure

The present disclosure relates to a job processing apparatus, a methodfor controlling a job processing apparatus, and a storage medium.

Description of the Related Art

Typical job processing apparatuses that execute jobs and store recordsof the executed jobs have been available.

Examples of such job processing apparatuses include one that displayssuch records of jobs on a home screen for selecting therefrom the copyfunction and the send function, as discussed in Japanese PatentApplication Laid-Open No. 2018-125686.

Thus displaying a list of the history records enables a user to easilycheck a history of jobs executed recently.

In typical techniques, job execution records can be displayed on a homescreen. However, the user cannot check whether an error has occurred.Thus, the user may select a job record without recognizing that an errorhas occurred to the selected job. As a result, the selected job recordis used for settings of a new job even though the error has occurred.

In that state, when a job execution instruction is received, theexecution of the job may possibly be suspended because of the error.

SUMMARY

According to embodiments of the present disclosure, a job processingapparatus includes an execution unit configured to execute a job, adisplay unit configured to display a plurality of history records withthe plurality of history records being arranged side by side inchronological order, the plurality of history records each indicating ahistory of a job executed by the execution unit, and a detection unitconfigured to detect an error. In response to the detection unit havingdetected an error, the display unit displays an error record with theerror record and the plurality of history records being arranged side byside, the error record indicating the error.

Further features of the present disclosure will become apparent from thefollowing description of exemplary embodiments with reference to theattached drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a configuration of an imageprocessing apparatus according to an exemplary embodiments.

FIG. 2 is an external view of an operation unit according to anexemplary embodiments.

FIG. 3 is a flowchart of processing from when the image processingapparatus is started up to when a screen for a logged-in user isdisplayed.

FIG. 4 is a schematic view of an authentication screen.

FIGS. 5A and 5B are schematic views of a home screen.

FIGS. 6A and 6B are schematic views of the home screen.

FIGS. 7A and 7B are schematic views of the home screen.

FIGS. 8A, 8B, and 8C are schematic views of the home screen.

FIG. 9 is a flowchart of processing that is performed from when anapplication is started up to when the execution of a job is completed.

FIGS. 10A and 10B are schematic views of a copy screen.

FIGS. 11A and 11B are schematic views of an error screen.

FIGS. 12A to 12D illustrate a data table saved in a memory area in thecopy function.

FIG. 13 is a flowchart of processing for generating respective names ofa setting button and a situation information button to be displayed inan integrated history.

FIGS. 14A to 14E illustrate a setting data table saved for theintegrated history.

FIGS. 15A, 15B, and 15C illustrate a setting data table saved for theintegrated history.

FIG. 16 is a flowchart of processing for generating text for settingvalues.

FIG. 17 is a flowchart of processing until a history is displayed in theintegrated history.

FIG. 18 is a flowchart of processing for calling up an application fromthe integrated history.

FIGS. 19A and 19B are schematic views of a situation explanation tablefrom which a state category and text to display is obtained from amongsituation categories.

FIG. 20 illustrates a correspondence table between explanation IDs anddisplay language text strings.

FIG. 21 is a schematic view of the error screen.

FIG. 22 is a relationship diagram between image processing systems.

FIG. 23 is a flowchart of processing for history information datatransfer.

FIG. 24 is a flowchart of processing for integrated history dataprocessing at log-out.

DESCRIPTION OF THE EMBODIMENTS

Exemplary embodiments will be described below in detail with referenceto the accompanying drawings. The following exemplary embodiments arenot seen to be limited. It is not necessarily the case that allcombinations of features described in the present exemplary embodimentsare deemed to be essential.

A first exemplary embodiment of the present disclosure will be describedbelow in detail. FIG. 1 is a block diagram illustrating theconfiguration of an image processing apparatus 1, which is an example ofa job processing apparatus according the present exemplary embodiment.

The image processing apparatus 1 includes a control unit 10, anoperation unit 12, an image processing unit 13, a scanner 140, and aprinter 141.

The control unit 10 controls operation of the units in the imageprocessing apparatus 1. The control unit 10 includes a CPU 100, acommunication unit 101, a random access memory (RAM) 102, a hard diskdrive (HDD) 103, a read-only memory (ROM) 104, a timer 105, a FAX unit106, a scanner interface 108, and a printer interface 109.

The CPU 100 controls the entire control unit 10. The RAM 102 functionsas a work memory for the CPU 100. The HDD 103 stores therein applicationprograms and image data. The HDD 103 may be a storage medium, such as anoptical medium or a flash memory. The ROM 104 stores therein a programread out by the CPU 100, such as a boot program. The HDD 103 may beconfigured in the form of an external storage apparatus to be detachablefrom the image processing apparatus 1.

The timer 105 manages a clock, to which the CPU 100 refers to acquiretime information.

The communication unit 101 is connected to a local area network (LAN) 11and controls data transmission and reception that are performed via theLAN 11. The FAX unit 106 is connected to a telephone line 14 andcontrols data transmission and reception that are performed via thetelephone line 14.

The operation unit 12 includes a display unit 120, having a touch panelsheet attached thereto, and an input unit 121, such as a hardware key.The operation unit 12 displays a screen and receives operations from auser, for example. In the present exemplary embodiments, a liquidcrystal display is taken as an example of the display unit 120. However,a display based on a different technique may be employed. In the presentexemplary embodiments, a touch panel is taken as an example of the inputunit 121. However, the input unit 121 may be configured to receiveoperations from a user via another interface, such as a mouse, an audioinput device, and a keyboard.

The image processing unit 13 is controlled by the control unit 10 andincludes an image analysis unit 130, an image generation unit 131, andan image output unit. The image analysis unit 130 analyzes the structureof an image of a document and extracts necessary information from theanalysis result. The image generation unit 131 reads a document usingthe scanner 140, thereby digitalizing an image of the document togenerate image data. The generated image data is stored in the HDD 103.The image generation unit 131 is also capable of generating documentimage data in another format using information obtained in analysisperformed by the image analysis unit 130.

The image processing apparatus 1 includes a copy function, a scannerfunction, and a print function. The copy function is a function forexecuting a copy job that includes reading a document using the scanner140 and causing the printer 141 to print an image on a sheet based onimage data about the document. The scanner function is a function forexecuting a send job that includes reading a document using the scanner140 and sending, using the communication unit 101, image data thusgenerated.

The print function is a function for executing a print job that includesprinting an image on a sheet based on print data received via thecommunication unit 101 from an external information processingapparatus, such as a personal computer (PC).

FIG. 2 is a schematic view of the operation unit 12 illustrated in FIG.1.

The touch panel 200 in this example has a touch panel sheet attached onthe liquid crystal display. The touch panel 200 displays an operationscreen and software keys and, when a key displayed is selected, notifiesthe CPU 100 of positional information about the key. Thus, the touchpanel 200 in the present exemplary embodiment functions as the displayunit 120 in FIG. 1 and also as the input unit 121 at the same time.

Next, various keys and buttons, which are operated by a user, will bedescribed. A start key 201 is used, for example, to instruct the scanner140 to start operation for reading a document. A light emitting diode(LED) unit 202 for two colors, green and red, is placed at the center ofthe start key 201 and indicates, by color, whether the start key 201 isin a usable state. A stop key 203 is used to stop operation that isbeing executed. The numeric keypad 204 is configured in the form of keyshaving numbers and marks and is used to set the number of copies or toinstruct the touch panel 200 to change screens. The user mode key 205 isused to call up a user mode. In the user mode, settings of imageprocessing apparatus 1 are made.

FIG. 3 is a flowchart illustrating user-login processing according tothe present exemplary embodiment. The processing of the flowchart inFIG. 3 is implemented by the CPU 100 reading a program stored in the ROM104 into the RAM 102 and executing the program. The processing of thisflowchart is started in response to startup of the image processingapparatus 1. The processing is also started in response to logout of auser from the image processing apparatus 1.

In step S301, the CPU 100 displays an authentication screen on theoperation unit 12. The screen 200 in FIG. 4 is an example of theauthentication screen. The screen 200 in FIG. 4 includes a usernameinput field 401, a password input field 402, and an OK button 403.

In step S302, the CPU 100 receives a username and a password from theuser via the operation unit 12. When the OK button 403 is pressed withthe username input field 401 having a username input thereto and withthe password input field 402 having a password input thereto, the CPU100 stores the input username and password in the HDD 103, and theprocessing proceeds to step S303. In addition to or instead ofconfiguring the CPU 100 to receive a username and a password that areinput by a user, the CPU 100 may be configured to read out a usernameand a password from a card.

In step S303, the CPU 100 compares, for each user, the username andpassword received in step S302 with usernames and passwords previouslyregistered in the HDD 103, thus determining whether the receivedusername and password match any username and password that have beenregistered.

If the CPU 100 determines that the username and password match any ofthe registered ones, the CPU 100 determines in step S304 thatauthentication is successful (YES, in step S304), and the processingthen proceeds to step S306. If the CPU 100 determines that the usernameand password do not match any of the registered ones, the CPU determinesin step S304 that authentication is not successful (No, in step S304),and the processing proceeds to step S305.

In step S305, the CPU 100 displays an error screen on the operation unit12, and the processing then proceeds to step S301. In step S306, the CPU100 reads information associated with the user.

In step S307, the CPU 100 allows the user to log in to the imageprocessing apparatus 1.

In step S308, the CPU 100 stores information about user currently loggedin.

In step S309, the CPU 100 display a screen for the logged-in user on theoperation unit 12.

FIGS. 5A and 5B illustrate a home screen for displaying objects forselecting the copy function and for selecting the send function, whichare displayed in response to login of a user to the image processingapparatus 1.

The home screen includes a menu 500 and an integrated history 509 foreach user.

In the menu 500, function selection buttons (a “Copy” button 501, a“Send” button 502, and a “FAX” button 503) for selecting a desiredfunction are displayed, and so are custom buttons for a user to call upsettings that have been previously set. Examples of the custom buttoninclude a “Contract” button 504, a “Written Request” button 505, and a“Send to Myself” button 506.

These buttons are displayed in a layout customized by the user based oninformation about the user who has logged in to the image processingapparatus 1. The buttons include “my buttons”, which are displayed onlyon a home screen for an individual user, and shared buttons, which aredisplayed also on home screens for all users.

The slider bar 507 is used for displaying buttons that cannot bedisplayed all at once. The slider bar 507 indicates that this menu 500can be slid to move. In response to the user sliding the slider bar 507,pressing an arrow, or flicking the menu 500, the CPU 100 calls up, fromthe HDD 103, an application button and a custom button that have beenregistered for the next area and displays these buttons.

In an upper right area 508, for displaying a username, a username of theuser who is currently logged in to the image processing apparatus 1 isdisplayed. FIG. 5A illustrates a state in which “User A” is currentlylogged in to the image processing apparatus 1.

The integrated history 509 (detailed down below) is an area in whichjobs are displayed as history records in chronological order ofexecution of the jobs, as a result of processing in which respectiveexecution records of jobs executed by this image processing apparatus 1for a plurality of applications are automatically registered inassociation with corresponding settings of the individual jobs. In theintegrated history 509, a job positioned lower is one executed earlierin time, and a job positioned higher is one executed later in time. Thatis, in higher positions, the integrated history 509 displays the historyrecords of jobs executed more recently. This configuration makes iteasier for the user to check the history records of jobs that have beenexecuted more recently without any operation performed on the slider bar507.

When a user has been logged in to the image processing apparatus 1, ahistory of only jobs executed in the past by the user who has logged inis displayed in the area of this integrated history 509. In the case ofthe user who has never executed any job, or in the case of the user whohas just deleted records on the integrated history 509, no records aredisplayed in the area for the integrated history 509 as illustrated inFIG. 5A.

Subsequent control on display of the integrated history 509 is executedby the CPU 100 based on an application for displaying an integratedhistory (hereinafter referred to as integrated history or integratedhistory application) stored in the HDD 103. Data to be used for theintegrated history is stored in the HDD 103.

FIG. 9 is a flowchart of the processing to be performed when a job isexecuted, according to the present exemplary embodiment. The processingof the flowchart in FIG. 9 is implemented by the CPU 100 reading acomputer program stored in the ROM 104 into the RAM 102 and executingthe read program. This processing of the flowchart is started inresponse to selection of the Copy button 501 on the image processingapparatus 1.

In step S601, the CPU 100 causes the operation unit 12 to display a copyscreen. The user makes settings for the number of copies,black-and-white or color, one-sided or two-sided reading, a copy ratio,and printing paper via the copy screen. The CPU 100 stores the receivedsettings in the HDD 103. FIG. 10A illustrates a copy screen 200. Thecopy screen 200 includes a color selection button 703, a copy ratiosetting button 704, a paper selection button 705, a finishing button706, a two-sided button 707, a density button 708, a document-typebutton 709, and an ID card copy button 710. The copy screen 200 furtherincludes an “other functions” button 711, a settings history button 712,and a frequently used setting button 713. The color selection button 703is used for setting whether to read a document in color orblack-and-white. The copy ratio setting button 704 is used for the copyratio setting for reading a document and printing the image of thedocument in an enlarged or reduced size. The paper selection button 705is used for selecting printing paper. The finishing button 706 is usedfor setting whether to make collated sets of copies from the first pagein printing the document and then output without stapling, or to makecollated sets of copies from the first page in printing the document andthen staple each set of copies and output the sets of copies. Thetwo-sided button 707 is used for setting whether to read only one sideof a document or read two sides of the document. The density button 708is used for setting the density of a printed image. The document-typebutton 709 is used for selecting whether the type of a document is text,text and picture, or picture. The ID card copy button 710 is used forsetting an ID card copy mode in which images on both sides of a documentare read and printed onto one side of a single piece of printing paper.

The “other functions” button 711 is used for making settings forfunctions (such as a punching function and a copy-forgery-inhibitedpattern printing function) other than the above-described functions. Thesettings history button 712 is used for displaying the history ofsettings for copy jobs executed in the past. The frequently used settingbutton 713 is used for displaying a screen for registering beforehand,editing, and calling up settings that each user frequently uses. A homebutton 714 is used for returning to the home screen.

A setting confirmation button 702 is used for displaying, in a list andin the form of text strings, settings for a copy job currently beingset.

An area 701 displaying setting values and respective displays on thebuttons on the screen illustrated in FIG. 10A indicate a state in whichblack-and-white is set for the color selection, 100% is set for the copyratio, automatic selection is set for the paper size, 1 is set as thenumber of copies, and collating is set.

The user thus makes copy settings and presses the start key 201 with thedocument placed on the scanner 140.

In step S602, the CPU 100 determines whether the start key 201 has beenpressed.

In step S603, the CPU 100 reads, from the HDD 103, information aboutsettings received via the copy screen illustrated in FIG. 10A andexecutes a copy job in accordance with the read settings.

In step S604, the CPU 100 stores information about settings of theexecuted copy job as a job execution history record in the HDD 103. Atthe same time, the CPU 100 stores temporal information acquired byreferring to the timer 105 as a part of the job execution historyrecord.

FIG. 12A represents an example of data saved in a memory area in the HDD103 for the copy function in step S604. As illustrated in a header 801of a data table in FIG. 12A, this table has setting values of theapplication recorded therein. A default setting row 802, which is thefirst row, has default setting values for the copy function savedtherein. A row for a most-recent settings row 803, which is the secondrow, has setting values additionally saved for a job that has beenexecuted for this time.

FIG. 13 illustrates processing of generating the names of buttons to bedisplayed in integrated history 509 on the application side. Theprocessing of the flowchart in FIG. 13 is implemented by the CPU 100reading a program stored in the ROM 104 into the RAM 102 and executingthe read program. This flowchart is executed in response to thecompletion of execution of the job in step S604 in FIG. 9.

After the process in step S604 in FIG. 9 is completed, in step S901, theCPU 100 acquires data about the integrated history 509 stored in the HDD103. FIG. 14A illustrates a data table saved for the integrated history509. As illustrated in a header 1001 of the data table, button IDs,application IDs, data types are stored. Data about setting values set onthe application or text data are stored. In addition, the data tablestores setting data set by the application, information about anapparatus detected by the application, situation categories, dates andtime, setting values of individual jobs, and/or text data indicatingsituations surrounding the job occurrence.

The button ID is used for uniquely identifying each history recordregistered in the integrated history 509. The application ID is used foridentifying which application has executed a job corresponding to ahistory record registered in the integrated history 509. The applicationID is previously determined for individual applications in such a mannerthat a management application of the image processing apparatus 1 itselfis assigned “100”, a copy application is assigned “101”, and a sendingapplication is assigned “201”.

The data type is used for identifying the category of a data main body(described down below). The data type “setting” represents job settingdata, and the data type “situation” represents situation informationdata about the image processing apparatus 1 itself or each job.

The “data” in the table indicates data about settings of a job executedby the corresponding application. For example, the application for copyincludes all functions and setting values, such as the number of copies,color selection, and the paper size, the settings of which are made onthe application.

The “text to display” in the table includes date and time and settingvalues. The setting value is a setting used in each job and/orinformation necessary for the application to manage the state of theimage processing apparatus 1. The situation category of the imageprocessing apparatus 1 itself and the situation category of each job areincluded in the state of the image processing apparatus 1. The situationcategory of the image processing apparatus 1 itself is, for example,information about the image processing apparatus 1 in which a failurehas occurred to a facsimile line as illustrated in a row 1006 in FIG.15A. The situation category of each job is, for example, a situationcategory regarding a specific job which, for example, includes an errorhaving occurred in sending an electronic mail as illustrated in a row1007 in FIG. 15B.

Such various data are stored in formats that can be read by applicationsthat registers the corresponding data. Date and time in the “text todisplay” is date and time when the corresponding job has been executedor when the corresponding application detects a situation of the imageprocessing apparatus 1 itself or each job, and is text data to bedisplayed on a button under the integrated history 509. The settingvalue in the “text to display” indicates either text data obtained bypicking up a characteristic setting among settings for each executed jobor a characteristic message that represents a situation of the imageprocessing apparatus 1 itself or the corresponding job. This settingvalue is also displayed on the button of the integrated history 509.These text strings of the date and time and the setting value enable theuser to browse the integrated history 509 to recall, about theindividual history records, specific settings with which each job hasbeen executed.

After acquiring data about the integrated history 509 in step S901, theCPU 100 determines in step S906 whether the situation in the imageprocessing apparatus 1 has changed.

If the CPU 100 determines that the situation has not changed (NO, instep S906), the processing proceeds to step S902. In step S902, the CPU100 then compares the acquired data with setting data about a jobexecuted for this time, thus checking whether any history record of thesame setting data has been stored in the integrated history 509. Thedata about the integrated history 509 is compared with the setting dataabout the job executed for this time for the purpose of avoidingduplication of records in the history. It is considered possible that,as a result of a duplication, the display area of the integrated history509, which is limited, may be filled up with data having the samesettings. A wider range of choices is made available to a user whoreuses the history with a list of jobs having a wider variety ofsettings compared with a list of jobs having the same settings. In thecurrent processing, there is no data to compare, and the CPU 100determines that the setting data about the job executed for this time isnot included in the existing history data. If the integrated history 509does not include data about the same history record (No, in step S902),the processing proceeds to step S903. In step S903, the CPU 100 startsprocess of generating text which is to be displayed in the integratedhistory 509 and corresponds to setting values.

FIG. 16 is a flowchart illustrating processing of generating text forsetting values. The processing of the flowchart in FIG. 16 isimplemented by the CPU 100 reading a computer program stored in the ROM104 into the RAM 102 and executing the read program.

At the start, in step S1107, the CPU 100 determines whether theapplication has been notified from the menu 500 of a name 1802, a nameof a custom button. The name is one piece of information among pieces ofinformation that the application is notified of when a job is executedin response to selection of any one of the custom buttons (504 to 506),which will be described in description of the operation of each custombutton. If the CPU 100 has determined that the application has beennotified of the name 1802 (YES, in step S1107), the processing proceedsto step S1109. In step S1109, the CPU 100 compares the setting values ofthe job executed this time with custom setting values. If the CPU 100determines that there is no difference in setting data (NO in stepS1109), the processing proceeds to step S1108. In step S1108, the CPU100 replaces TXT data in step S1108 with the name 1802 of which theapplication has been notified, and the processing ends. If the CPU 100determines in step 1107 that the application has not been notified ofthe name (No, in step S1107), the processing proceeds to step S1101. Ifthe CPU 100 determines in step S1109 that settings for the job have beenchanged from the custom settings with the application having beennotified of the name 1802 (YES, in step S1109), the processing proceedsto step S1102.

If the processing proceeds from step S1107 to step S1101, the CPU 100compares setting values of the job executed for this time with settingvalues of the default settings. Specifically, the CPU 100 performs thecomparison of the setting values in FIG. 12A sequentially from the leftitem to the right item. In this example, the CPU 100 compares thesetting value for the number of copies in the first place. If there ismore than or equal to one difference as a result of the comparison (YES,in step S1101), the processing proceeds to step S1102. In step S1102,the CPU 100 acquires text corresponding to the setting values includingthe difference. The reason for picking up a difference between thesettings for the corresponding job and the default settings is that anitem for which the user has deliberately changed the setting value isconsidered to have been more memorable. In this example, there is adifference in the number of copies in the first place, and the text thatis first acquired by the CPU 100 is “2 Copies”. Subsequently, in stepS1103, the CPU 100 acquires the length of the text. Each buttondisplayed in the integrated history 509 is limited in the length of thetext. Thus, in step S1104, the CPU 100 checks whether the length of thetext exceeds the upper limit of the displayable range. If the CPU 100then determines that the length exceeds the upper limit of thedisplayable range (YES in step S1104), corresponding text data is notadded, and the processing of generating text to display ends. If the CPU100 determines that the upper limit is not exceeded (NO, in step S1104),the processing proceeds to step S1105. In step S1105, the text data thathas been acquired (loaded) is added as text data to be displayed in theintegrated history 509 by the CPU 100 for the setting value. If there isa difference for any of the remaining setting values (YES, in stepS1106), the processing proceeds to step S1102 and the CPU 100 repeatsthe processing in steps S1102 to S1105. If all pieces of the settingdata having differences have been processed before the upper limit ofthe displayable range is exceeded, the processing of generating textdata ends as well. In this example, two-sided setting is the last itemfor which the setting value has a difference. Thus, all that isgenerated as text data is “2 Copies, Color, 2-Sided”. The setting valuesfor the rest of the items have no differences, and thus, data forsetting value text is completed by including the data for two-sidedsetting. Finally, the application ID of the application that is executedby the CPU 100 and the setting data of this job that have been saved inthe HDD 103 in step S604 in FIG. 9 are saved as data1.xml. Along withthis process, the CPU 100 saves in the HDD 103 the generated settingvalue text, text for job execution date and time, and information aboutthe presence of existing data, and sends those pieces of information tothe integrated history 509 in step S904. Information about the presenceof the existing data results from the comparison in step S902.

In the above-described manner, an object to be displayed in theintegrated history 509 is registered.

Next, the case where the processing proceeds to step S907 with thedetermination of YES in step S906 will be described. For example, if afailure occurring in the facsimile line is detected, the processingproceeds from step S906 to step S907. The image processing apparatus 1includes a “state monitoring application” for monitoring the state ofthe image processing apparatus 1 itself. The state monitoringapplication is stored in the HDD 103 and is read into the RAM 102 andexecuted by the CPU 100.

In step S901, the CPU 100 acquires data saved in the HDD 103 forintegrated history 509. A data table saved for the integrated history509 is in a state illustrated in FIG. 14E.

If the CPU 100 has determined in step S906 that the situation of theimage processing apparatus 1 has changed (YES, in step S906), theprocessing proceeds to step S907. In step S907, the CPU 100 determineswhether a new situation has occurred. If the CPU 100 determines that aline disconnection has occurred as a new situation (YES, in step S907),the processing proceeds to step S908. In step S908, the CPU 100 acquiresa state category and explanatory text to be displayed, from a detectedsituation category in accordance with a situation explanation tableillustrated in FIG. 19A. The CPU 100 acquires the statecategory=“warning” (1404) and an explanation ID=“MSG_ID_FAX_LINEOFF”(1405) that correspond to the situation category=“line” (1402) and thestate=“disconnection” (1403). The state category=“warning” indicates astate in which the use of the image processing apparatus 1 or anyapplication that is affected by the state is to be stopped.

Subsequently, the CPU 100 executes the state monitoring application,thus referring to a correspondence table of explanation IDs and displaylanguage text strings illustrated in FIG. 20. Then in step S908, the CPU100 acquires situation text (TXT)=“Please check FAX line” (1503) withthe language thereof corresponding to the display language set in theoperation unit 12 based on the acquired explanationID=“MSG_ID_FAX_LINEOFF”. Finally, in step S909, the CPU 100 sends theacquired state category=“warning” (1404) and a display textstring=“Please check FAX line” (1503) as situation TXT to the integratedhistory 509. Here, the CPU 100 sends these pieces of information, thesituation category, and the state, together with the application ID, thedata type, the situation TXT, date and time TXT, and informationindicating the absence of existing data, to the integrated history 509with the situation category and the state being grouped as situationinformation data=“FAXLINE_ERROR.xml”. Thus, the state of the data tablesaved for the integrated history 509 changes to the one as illustratedin FIG. 15A and a screen for the integrated history 509 becomes thescreen as illustrated in FIG. 8A. In FIG. 8A, an error record 517 isdisplayed in priority to other history records 514 to 516 and in aposition higher than positions at which the history records 514 to 516are displayed. The error record 517 includes an alarming icon in theleft part thereof.

If it is detected here that the facsimile line has recovered from thedisconnection, the CPU 100 generates “line” as a situation category and“normal” as a state. The situation category=“line” is already in theintegrated history 509. The state monitoring application thus determinesthat this situation is not a situation that has newly occurred (NO instep S907), and the processing proceeds to step S910. In step S910, theCPU 100 requests the integrated history 509 to delete that information,and the processing proceeds to step S911. In step S911, the CPU 100determines whether the situation has been resolved. If the CPU 100determines in step S911 that a situation other than the statecategory=“normal” has not been resolved (No, in step S911), theprocessing proceeds to step S908. In step S908, the CPU 100 performs thesame processing as the processing which is to be performed when a newsituation has occurred. Thus, situation information about a new state isdisplayed in the integrated history 509. The state category thatcorresponds to the situation category=“line” and the state=“normal” forthis time is “normal”. Thus, the CPU 100 determines in step S911 thatthe situation has been resolved (YES in step S911), and the processingends without any further processing being performed. Thus, the situationthat has been displayed in the integrated history 509 disappears.

While the above description has been provided using a case in which theCPU 100 has detected a situation of line disconnection, a similaroperation is performed also when an application to which a job is inputhas detected a state that the user needs to be notified of.

For example, suppose that the copy application has been instructed toexecute a job with a stapling setting while the maximum number of sheetsthat can be stapled is exceeded in the apparatus. The operation when theuser executes a copy job has been described above, and thus descriptionwill be provided here only of operation that is performed when asituation of some sort that the user needs to be notified of hasoccurred.

First, the copy application reads, with set conditions, a documentplaced by the user and calculates the total number of pieces of paperthat need to be output. This example assumes that the copy applicationhas determined that the total number of output pieces exceeded themaximum number of sheets that can be stapled. Based on this situation,the copy application generates a situation category=“execution”, astate=“Too many sheets to staple”, and a state category=“alert”. Thestate category=“alert” is a state category for which the execution ofthe job is not stopped but the user needs to be alerted. Thus, it isdetermined in step S906 that the situation of the copy application thatis to be executed by the CPU 100 has changed. The copy application thendetermines in step S907 whether a new situation has occurred. If thestate monitoring application determines that the situationcategory=“execution” is a situation that has newly occurred, the copyapplication acquires a state category and explanatory text to bedisplayed, from the situation category detected by the copy applicationin accordance with a situation explanation table illustrated in FIG.19B. The copy application acquires an explanationID=“MSG_ID_COPY_STAPLEOVER” (1407) that corresponds to the situationcategory=“execution” (1409) and the state=“Too many sheets to staple”(1406). Subsequently, based on the correspondence table of explanationIDs and display language text strings illustrated in FIG. 20, the copyapplication acquires situation TXT=“Too many sheets to staple” (1505) inthe display language of the operation unit 12 based on the acquiredexplanation ID=“MSG_ID_COPY_STAPLEOVER” (1504) (step S908). Finally, instep S909, the CPU 100 sends the acquired state category=“alert” (1407)and a display text string=“Too many sheets to staple” (1505) assituation TXT to the integrated history 509. Here, the CPU 100 sendsthese pieces of information, the situation category, and the state,together with the application ID, a data type, the situation TXT, anddate and time TXT, and information indicating the absence of existingdata, to the integrated history 509 with the situation category and thestate being grouped as situation information data=“STAPLEOVER.xml” (stepS909). Thus, the state of the data table saved for the integratedhistory 509 changes to the state as illustrated in FIG. 15B and a screenfor the integrated history 509 becomes the screen as illustrated in FIG.8B. In FIG. 8B, an error record 518 is displayed in priority to theother history records 514 to 516 and in a position higher than positionsat which the history records 514 to 516 are displayed. The error record518 includes, in the left part thereof, an icon that indicates an error.

FIG. 17 is a flowchart of processing up to the point where theintegrated history 509 that has received the above setting informationdata or situation information data displays a history.

In step S1201, the integrated history 509 that is executed by the CPU100 receives the values saved in the HDD 103 in step S604 in FIG. 9 fromthe application that is executed by the CPU 100. Subsequently, in stepS1202, the CPU 100 determines whether the received data are settingdata. If the CPU determines that the received data is setting data, theprocessing proceeds to step S1203. In step S1203, the CPU 100 checkswhether there is existing data. If the CPU 100 determines that there isno existing data (NO, in step S1203), the processing proceeds to stepS1204. In step S1204, the CPU 100 newly adds the data received from theapplication in the data table of the integrated history 509. The datareceived from the application are added in the data table as illustratedin FIG. 14B. If the CPU 100 determines that there is existing data (YES,in step S1203), the processing proceeds to step S1205. In step S1205,the CPU 100 performs nothing other than updating the date and time.

If the CPU 100 determines that the received data are not setting data(NO, in step S1202), the processing proceeds to step S1206. In stepS1206, the CPU 100 checks whether there is existing data. If the CPU 100determines that there is no existing data (NO, in step S1206), theprocessing proceeds to step S1207. In step S1207, the CPU 100 newly addsthe data received from the application in the data table for theintegrated history 509. The data received from the application are addedin the data table as illustrated for a button ID 1003 in FIG. 14E. Ifthere is existing data, the CPU 100 performs nothing other than updatingthe date and time in step S1208.

The screen of the operation unit 12 is still a copy screen, and the CPU100 displays the home screen in FIG. 5B in response to selection of thehome button 714. As illustrated in FIG. 5B, the home screen for the userA is displayed with a button 510 for a history record for this timedisplayed in the integrated history 509. In the history button (alsoreferred to as button or history record) 510 for this time, an icon 511for the application identified from the application ID, job executiondate and time 512, and text 513 that represents differences from thedefault settings are displayed. The icon 511 for the application is anicon for a copy job. An icon for a send job is displayed as an icon in ahistory record 515 in FIG. 6B. This information is important to help theuser to, when browsing the history record 510, recall specific settingswith which the corresponding job has been executed. When the user wishesto execute a new job with the same settings, the CPU 100 performs, inresponse to the user having pressed the history record 510, processingfor calling up the application with the same settings reflected in thejob.

The processing of calling up an application from the integrated history509 will be described with reference to FIG. 18. The processing offlowchart in FIG. 18 is implemented by the CPU 100 reading a computerprogram stored in the ROM 104 into the RAM 102 and executing the readprogram.

In response to the user selecting the history record 510 (also referredto as history record or object) in the integrated history 509 in FIG.5B, the CPU 100 reads in step 1301, from the data table saved in the HDD103 for the integrated history 509, data for a history that correspondsto the selected button ID. The integrated history 509 determines atarget application from an application ID in history data that is readout, and sends setting data to the target application in step S1302.Copy is to be performed in this example, and thus, the copy applicationis called up by the CPU 100. In step S1303, the copy application thatruns on the CPU 100 reads setting values for various settings from thereceived data, and displays a screen for the application on theoperation unit 12 with the settings reflected therein. FIG. 10Billustrates a copy screen displayed with settings in the history record510 reflected therein.

By thus using the integrated history 509, the user can call the settingswith which the user has executed a job with a single touch and use thesettings.

Next, a description will be provided of a case of executing a job with achange in some of the settings called up from the integrated history509.

In this example, suppose that the user has changed only the number ofcopies to five among the above settings of the current job in step S602and pressed the start key 201. In step S603, the application that runson the CPU 100 executes a job in accordance with specific settings. Instep S604, the CPU 100 overwrites the settings of a job at the time ofexecuting the job with settings as illustrated in a row 804, which isthe second row, in FIG. 12B and saves the overwritten settings.Thereafter, in a manner similar to that described above, the currentsetting data are compared with existing data in the integrated history509, as in the processing of the flowchart in FIG. 13. The currentsettings are not assumed to be included in the existing data in thisexample, text corresponding to a difference in settings is generated inaccordance with the flowchart in FIG. 16, and various data are sent tothe integrated history 509. Thereafter, a history record with newsettings is added in accordance with the flowchart in FIG. 17. FIG. 14Crepresents a history having a row 1003 newly added to the data table.FIG. 6A is a screen on which the history 514 is newly displayed in theintegrated history 509 on the home screen. In the integrated history509, jobs are sorted in descending order of execution date and timethereof and displayed while being arranged side by side, and thus, anewly added job history record is added in the topmost position asillustrated in FIG. 6A.

Thus using the job settings once used by the user can save the user fromhaving to make job settings.

When the user selects the history record 510, in FIG. 6A, of a copy jobfirst executed and executes a job without changing any settings, the CPU100 makes a determination of YES for the determination as to whetherthere is existing data in the integrated history 509 in step S902 inFIG. 13. Thus, the processing in step S903 for generating text is notexecuted. In step S905, data about date and time text, informationindicating the presence of existing ID, and information about whichbutton ID in the integrated history 509 corresponds thereto are sent tothe integrated history 509 from the application. Since there is anexisting ID, in the process of step S1202, which is to determine whetherthere is existing ID for processing of perform saving into data for theintegrated history 509 in FIG. 17, it is determined that there is theexisting ID. In step S1204, the CPU 100 updates only a date in data, inFIG. 14D, the button ID of which is matched.

FIG. 14E represents data 1005 with a date updated. The integratedhistory 509 displays history records in descending order of date andtime thereof, and thus the copy history record 516 that has been themost recently executed is in the topmost position in the setting historyas in FIG. 7A.

Next, a description will be provided of a case of returning to the homescreen without execution of a job after calling up settings of thecorresponding job in response to selection of the send history record515 in FIG. 7A. In such a case, the processing in step S604, in whichsettings are saved, and the subsequent steps in FIG. 9 is not performedbecause a job is not executed. Accordingly, processing for updatinghistory data is not performed, and display is unchanged from the one inFIG. 7A.

Next, processing of calling up an application from the integratedhistory 509 will be described with reference to FIG. 18.

Suppose that the current screen is FIG. 8A and data for the integratedhistory 509 is the data as illustrated in FIG. 15A.

When the user presses the error record 517 in the integrated history509, the integrated history 509 that runs on the CPU 100 reads out, fromthe data table in FIG. 15A for the integrated history 509 that is savedin the HDD 103, data about a history record of the button ID=1004 thathas been pressed. The integrated history 509 determines, based on theapplication ID=100 in the read history record data, that a targetapplication is the state monitoring application. In step S1302, theintegrated history 509 sends the situation informationdata=“FAXLINE_ERROR.xml” to the state monitoring application. The statemonitoring application that runs on the CPU 100 reads a situationcategory and a state from the received situation informationdata=“FAXLINE_ERROR.xml”. The state monitoring application then checksthe current situation of the situation category=“LINE” and displays, onthe touch panel 200, a screen providing a guidance for resolving thesituation in step S1303. FIG. 21 illustrates a state monitoringapplication screen displayed with the situation of the error record 517reflected therein.

As described above, the integrated history 509 enables the user todisplay a desired situation with a one touch button.

Similarly, the user is enabled to display information about the copyapplication in each of the states of FIG. 8B and FIG. 15B with a singlebutton. A description of this operation will be provided below.

When the user presses the error record 518 in the integrated history509, the integrated history 509 that runs on the CPU 100 reads out, fromthe data table in FIG. 15B for the integrated history 509 that is savedin the HDD 103, data for a history record of the button ID=1004 that hasbeen pressed. The integrated history 509 determines, from theapplication ID=101 in the read history record data, that a targetapplication is the copy application. In step S1302, the integratedhistory 509 sends the situation information data=“STAPLEOVER.xml” to thecopy application. The copy application that runs on the CPU 100 reads asituation category and a state from the received situation informationdata=“STAPLEOVER.xml”. In step S1303, the copy application then displaysa screen suitable for the situation category=“execution” and thestate=“Too many sheets to staple” on the operation unit 12. FIG. 8Billustrates a state monitoring application screen displayed with thesituation of the error record 518 reflected therein.

If a copy job is being suspended Job because paper has run out, the copyapplication generates a situation category=“execution”, a state=“out ofpaper”, a state category=“suspended” (1408), whereby the integratedhistory data become as illustrated in FIG. 15C and a screen in FIG. 8Cis displayed. In FIG. 8C, an error record 519 is displayed in priorityto the other history records 514 to 516 and in a position higher thanpositions at which the history records 514 to 516 are displayed. Theerror record 519 contains, in the left part thereof, the icon thatindicates an error. When the user selects this error record 519, thecopy application displays a sheet feed cassette selection screen asillustrated in FIG. 11B. If the user then specifies a sheet feedcassette containing paper or loads the selected sheet feed cassette withpaper, the copy application determines that the out-of-paper state hasbeen resolved and starts the suspended copy job. At the same time, asalready described above, since the out-of-paper state has been resolved,the copy application detects this situation change in step S907 andaccordingly requests the integrated history 509 to delete the situationinformation, and the processing ends with further process not beingperformed, as the situation has been resolved. Thus, the integratedhistory data becomes the screen as illustrated in FIG. 14E, and the homescreen becomes the screen as illustrated in FIG. 7A, which enables theuser to recognize that there is no situation that the user needs to dealwith.

Next, operations of registration to and deletion from a menu of theintegrated history 509 will be described.

Each button displayed in the integrated history 509 functions to displaya context menu 580 for the button itself as illustrated in FIG. 7B whenthe user performs a pressing and holding operation on the button.Although the pressing and holding operation is taken as an example of auser operation for displaying the context menu 580, a method for callingup the context menu 580 is not limited to the pressing and holdingoperation and may be a double tapping operation, the arrangement of acall-up button, or the like. The context menu 580 provides, asoperations on each button in the integrated history 509, context menuoptions such as “Execute” 581, “Register in Menu” 582, and “Delete” 583.

When the “Execute” 581 is selected in FIG. 7B, the CPU 100 performsprocessing for calling up a corresponding application as alreadydescribed with reference to FIG. 18. When the “Register in Menu” 582 isselected in FIG. 7B, the CPU 100 performs processing for registering acustom button, as a new button, in the menu 500 in the left-hand side.Possible processing for determining the position of the button to beregistered is to set the button in a blank space within the menu 500 orto cause the user to select the position.

When the “Delete” 583 is pressed by the user in FIG. 7B, the CPU 100executes processing for deleting a selected history record. The CPU 100deletes the target record from the data table in which history recordsare arranged in chronological order and the data table for theintegrated history 509, and executes sorting of the remaining historyrecords by date and time thereof.

If the CPU 100 determines that a selected button in the integratedhistory 509 is not a button for setting but a button for situationinformation, the CPU 100 does not display the “Register in Menu” 582 onthe menu 580 and displays only the “Execute” 581 and the “Delete” 583.

Next, a description will be provided of a case in which the number ofhistory records or error records on the integrated history 509 hasreached an upper limit.

When the upper limit for the number of history records that can be savedin the integrated history 509 is reached after jobs with differentsettings have been repeatedly executed, the CPU 100 performs processingfor deleting history records sequentially from the data table inchronological order. This upper limit is the upper limit for the storagearea and is not necessarily the same as the upper limit for the displayarea. This is because the upper limit for the display area is variabledepending on configurations, such as the sizes and/or the layouts ofbuttons and functions, such as whether a screen is made scrollable witha slider bar or by flicking.

According to the present exemplary embodiment, the user is enabled tocheck a history of jobs with history records on a screen with which theuser is able to select the copy function and the send function, andeasily check, with an error record, whether an error has occurred.Moreover, according to the present disclosure, an error record isdisplayed in priority to history records and in a position higher thanpositions at which the history records are displayed, which enables theuser to be easily aware of the error when an error has occurred. Theerror record is displayed with date and time when error has occurred,which makes it easier for the user to check when the error has occurred,with the error record.

A second exemplary embodiment of the present disclosure will bedescribed below. In the present exemplary embodiment, a description willbe provided of processing for image processing apparatuses to share theabove described integrated history data.

FIG. 22 schematically illustrates the relationship among imageprocessing apparatuses.

An image processing apparatus 1, an image processing apparatus 2, and animage processing apparatus 3 each have the functions as described aboveand are connected to one another via a LAN as illustrated.

The authentication described with reference to FIG. 3 is also linkedamong one another, and a user who can be authenticated by the imageprocessing apparatus 1 can also be authenticated as the same user by theimage processing apparatuses 2 and 3. In this example, the imageprocessing apparatus 1 also serves as an authentication server function.

Assume that the user A is browsing the screen of FIG. 8A on the imageprocessing apparatus 1 and the integrated history data 509 is in thestate in FIG. 15A. If the user A is logged in to the image processingapparatus 2 in this state and a setting for identifying a user is “ON”on the image processing apparatus 2, the CPU 100 in the image processingapparatus 2 displays an authentication screen on the touch panel 200(step S301) after the main body of the image processing apparatus 2 isstarted up. FIG. 4 illustrates the authentication screen displayed onthe image processing apparatus 2. The authentication screen includesareas for inputting a username 401 and a password 402. After displayingthe authentication screen, the image processing apparatus 2 enters intoa state waiting for input of the username and the password (step S302).When the user inputs previously registered username and password andpresses the OK button 403, the CPU 100 sends this information to theimage processing apparatus 1. The image processing apparatus 1 comparesthe input username and password with usernames and passwords saved inthe HDD 103, thereby determining whether the received username andpassword match any of the saved usernames and passwords (step S303). Ifthe username and password do not match any of them, the image processingapparatus 1 returns an authentication error to the image processingapparatus 2 (step S304). In response to receiving the authenticationerror, the CPU 100 of the image processing apparatus 2 displays an errormessage on the touch panel 200 and displays the authentication screenagain (step S305). If the image processing apparatus 1 determines thatthe received username and password match any of the saved usernames andpasswords, the CPU 100 of the image processing apparatus 1 calls upinformation that is associated with the user and is saved in the HDD103, and sends the information to the image processing apparatus 2 (stepS306). In this sending, if history information data is to be sent toanother apparatus, the data to be sent is generated in accordance withthe processing of the flowchart illustrated in FIG. 23. In step S1801, aread position [i] of the history information data and a write position[j] of the data to be sent are initialized to zero. In step S1802, theCPU 100 of the image processing apparatus 1 checks whether data [i] inthe history information data is present. If the CPU 100 determines thatthe data [i] is present (YES, in step S1802), the processing proceeds tostep S1803. In step S1803, the CPU 100 reads the data [i]. In stepS1804, the CPU 100 checks whether the data type thereof is “setting”. Ifthe CPU 100 determines that the data type is “setting” (YES, in stepS1804), the processing proceeds to step S1805. In step S1805, the CPU100 sets the read data [i] to transfer data [j]. In step S1806, the CPU100 increments, by one, the read position [i] of the history informationdata and the write position [j] of the data to be sent. If the CPU 100determines that the data type is not “setting” (NO, in step S1804), theprocessing proceeds to step S1807. In step S1807, the CPU 100 incrementsthe read position [i] of the history information data by one.Thereafter, the processing proceeds to step S1802. In step S1802, theCPU 100 checks whether data [i] corresponding to the read position [i]in updated history information data is present. If the CPU 100determines that the data [i] to be read out is not present (No, in stepS1802), the processing proceeds to step S1808. In step S1808, the CPU100 sends the data to be sent. In response to completion of call-up ofthe information associated with the user, the CPU 100 of the imageprocessing apparatus 2 permits login of the user (step S307), and savesthe information as information about a currently logged-in user in theHDD 103 in the image processing apparatus 2 (step S308). Thereafter, theCPU 100 of the image processing apparatus 2 displays, on the touch panel200, a home screen in which the information on the logged-in user isreflected (step S309). At this point of time, the history informationdata about the user A in the image processing apparatus 2 is the data asillustrated in FIG. 14E, and the screen in FIG. 7A is displayed as thehome screen for the user A.

After the user A logs out, the image processing apparatus 2 sends userinformation about the user A to the image processing apparatus 1 so thatuser information of the user A can be updated.

According to the present exemplary embodiment, the image processingapparatuses can share the above-described integrated history data,history records and error records can be checked even when a differentimage processing apparatus is used.

A third exemplary embodiment of the present disclosure will be describedbelow. In the above-described exemplary embodiments, the setting dataand the situation information data are managed in a similar manner andare equally categorized by data type. In the present exemplaryembodiment, an example in which the situation information data arecompletely deleted when the user logs out is illustrated.

Only differences from the first exemplary embodiment will be describedbelow.

Referring now to the flowchart in FIG. 24, in response to receiving alog-out instruction, in step S1901, the CPU 100 initializes a readposition [i] of the history information data and a write position [j] ofthe data to be saved to zero. In step S1902, the CPU 100 checks whetherdata [i] in the history information data is present. If the CPU 100determines that the data [i] is present (YES, in step S1902), theprocessing proceeds to step S1903. In step S1903, the CPU 100 reads thedata [i]. In step S1904, the CPU 100 checks whether the data typethereof is “setting”. If the CPU 100 determines that the data type is“setting” (YES, in step S1904), the processing proceeds to step S1905.In step S1905, the CPU 100 sets the read data [i] to the saved data [j].In step S1906, the CPU 100 increments, by one, read position [i] of thehistory information data and the write position [j] of the saved data.If the CPU 100 determines that the data type is not “setting” (NO, instep S1904), the processing proceeds to step S1907. In step S1907, theCPU 100 increments by one the read position [i] of the historyinformation data. The processing then proceeds to step S1902. In stepS1902, the CPU checks whether data [i]corresponding to the read position[i] in updated history information data is present. If the CPU 100determines that the data [i] to be read is not present (No, in stepS1902), the processing proceeds to step S1908. In step S1908, the CPU100 overwrites the data with the saved data and saves the data. Thus,integrated history data processing at log-out is performed even with thehistory information data being in the state illustrated in FIG. 15B orFIG. 15C, whereby data 1006 the data type of which is not setting is notsaved, and, as a result, the history information data is saved in thestate illustrated in FIG. 14E.

When the user logs in again, situations that are managed by each of theapplications are registered in the integrated history 509. If thehistory information data before the log-out is data illustrated in FIG.15A and the situation thereof is unchanged, the state monitoringapplication for the entire apparatus registers data similar to the data1006 as a new situation occurring at that point, as in the processingdescribed in the first exemplary embodiment. However, the date and timefor the new situation is recorded as those when it has been detected asa new situation.

If the history information data before log-out is data illustrated inFIG. 15B, a situation having too many sheets to staple in a copy job hasnot occurred, and the copy application does not register the situation.The history information data therefore starts from the state in FIG.15B.

According to the present exemplary embodiment, the situation informationdata is completely deleted when the user logs out, which eliminates theneed to re-display situations once checked by the user.

Other Embodiments

Embodiment(s) of the present disclosure can also be realized by acomputer of a system or apparatus that reads out and executes computerexecutable instructions (e.g., one or more programs) recorded on astorage medium (which may also be referred to more fully as a‘non-transitory computer-readable storage medium’) to perform thefunctions of one or more of the above-described embodiment(s) and/orthat includes one or more circuits (e.g., application specificintegrated circuit (ASIC)) for performing the functions of one or moreof the above-described embodiment(s), and by a method performed by thecomputer of the system or apparatus by, for example, reading out andexecuting the computer executable instructions from the storage mediumto perform the functions of one or more of the above-describedembodiment(s) and/or controlling the one or more circuits to perform thefunctions of one or more of the above-described embodiment(s). Thecomputer may comprise one or more processors (e.g., central processingunit (CPU), micro processing unit (MPU)) and may include a network ofseparate computers or separate processors to read out and execute thecomputer executable instructions. The computer executable instructionsmay be provided to the computer, for example, from a network or thestorage medium. The storage medium may include, for example, one or moreof a hard disk, a random-access memory (RAM), a read only memory (ROM),a storage of distributed computing systems, an optical disk (such as acompact disc (CD), digital versatile disc (DVD), or Blu-ray Disc (BD)™),a flash memory device, a memory card, and the like.

While exemplary embodiments have been described, it is to be understoodthat the disclosure is not limited to the disclosed exemplaryembodiments. The scope of the following claims is to be accorded thebroadest interpretation so as to encompass all such modifications andequivalent structures and functions.

This application claims the benefit of Japanese Patent Application No.2018-215640, filed Nov. 16, 2018, which is hereby incorporated byreference herein in its entirety.

What is claimed is:
 1. A job processing apparatus which executes a job,comprising: a display that is able to display a plurality of historyrecords so that the plurality of history records are arranged side byside in chronological order, the plurality of history records eachindicating a history of an executed job; and a controller that detects apredetermined error, wherein, in a case where the controller detects thepredetermined error, the display displays an error record correspondingto the predetermined error so that the error record and the plurality ofhistory records are arranged side by side.
 2. The job processingapparatus according to claim 1, wherein the display displays, on ascreen including an object for selecting a copy function and an objectfor selecting a send function, the plurality of history records so thatthe plurality of history records are arranged side by side inchronological order, the plurality of history records each indicating ahistory of an executed job.
 3. The job processing apparatus according toclaim 2, wherein the job processing apparatus allows a user to be loggedin to the job processing apparatus, and wherein the display displays thescreen in response to the job processing apparatus having logged theuser in to the job processing apparatus.
 4. The job processing apparatusaccording to claim 1, wherein the job processing apparatus allows a userto be logged in to the job processing apparatus, and wherein the displaydisplays, on a home screen that is displayed in response to the jobprocessing apparatus having logged the user in to the job processingapparatus, the plurality of history records so that the plurality ofhistory records are arranged side by side in chronological order, theplurality of history records each indicating a history of an executedjob.
 5. The job processing apparatus according to claim 1, wherein thedisplay displays the error record in priority to the plurality ofhistory records.
 6. The job processing apparatus according to claim 1,wherein the error record indicates the predetermined error.
 7. The jobprocessing apparatus according to claim 1, wherein display of the errorrecord is ended in response to resolution of the predetermined error. 8.The job processing apparatus according to claim 1, wherein the pluralityof history records each includes an icon indicating a type of job whichis executed, and the error record includes an icon different from theicon indicating the type of job.
 9. The job processing apparatusaccording to claim 1, wherein the plurality of history records eachincludes a setting of a job which is executed.
 10. The job processingapparatus according to claim 9, wherein the job processing apparatuscalls up, in response to any one of the plurality of history recordshaving been selected by a user, a setting of a job that is included inthe selected history record and sets, as a setting of a new job, thecalled up setting.
 11. The job processing apparatus according to claim1, wherein the error record includes date and time at which thepredetermined error occurs.
 12. The job processing apparatus accordingto claim 1, wherein, when the error record is selected by the user, thedisplay displays a guidance for resolving the predetermined error. 13.The job processing apparatus according to claim 1, wherein each of theplurality of history records includes execution date and time at whichthe job processing apparatus executes a job.
 14. The job processingapparatus according to claim 1, wherein the job is a copy job or a sendjob.
 15. A method for controlling a job processing apparatus whichexecutes a job, the method comprising: displaying a plurality of historyrecords with the plurality of history records being arranged side byside in chronological order, the plurality of history records eachindicating a history of an executed job; and detecting a predeterminederror, wherein, in a case where the predetermined error is detected, anerror record corresponding to the detected predetermined error isdisplayed so that the error record and the plurality of history recordsare arranged side by side.
 16. A non-transitory computer-readablestorage medium storing a program for causing a computer to execute amethod for controlling a job processing apparatus which executes a job,the method comprising: executing jobs; displaying a plurality of historyrecords with the plurality of history records being arranged side byside in chronological order, the plurality of history records eachindicating a history of an executed job; and displaying, in a case wherethe predetermined error is detected, an error record corresponding tothe detected predetermined error so that the error record and theplurality of history records are arranged side by side.
 17. A jobprocessing apparatus which executes a job, comprising: a display that isable to display a plurality of history records with the plurality ofhistory records being arranged side by side in chronological order, theplurality of history records each indicating a history of an executedjob; and a controller that detects a predetermined error, wherein thedisplay displays an error record corresponding to the detectedpredetermined error so that the error record and the plurality ofhistory records are arranged side by side.